-
Notifications
You must be signed in to change notification settings - Fork 12.9k
Remove getNonNullableType application in checkIdentifier #60523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Out of pure curiosity - do you know why this doesn't regress the tests introduced by #50092 ? :p |
That PR's test didn't seem to enable strict mode... |
Enabling strict mode in that test causes |
@typescript-bot test it |
Hey @jakebailey, the results of running the DT tests are ready. Everything looks the same! |
@jakebailey Here are the results of running the user tests with tsc comparing Something interesting changed - please have a look. Details
|
@jakebailey Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
@jakebailey Here are the results of running the top 400 repos with tsc comparing Something interesting changed - please have a look. Details
|
This feels like something that shouldn't be required in strict mode without reporting an error or the need to add an assertion or smth: TS playground. This All other breaks reported above look basically the same to me. They assign to an unannotated variable from within a callback and then access that auto-typed variable with a non-null assertion. |
Fixes #60514